Activity: Submit Change Request

Purpose The purpose of having a standard, documented change control process is to ensure that changes are made within a project in a consistent manner and the appropriate stakeholders are informed of the state of the product, changes to it and the cost and schedule impact of these changes. Any worker may submit a change request against any configuration item throughout the project lifecycle.
Steps Complete Change Request Form Submit the Change Request
Resulting Artifacts: Change Request
Frequency: Once a configuration item has been baselined and entered into the configuration management system, all requests to changes to it should go through the official change request management process.
Worker: Any Worker
Tool Mentors Submitting a Change Request Using Rational ClearQuest«
More Information: Concepts: Change Request Management

Workflow Details:

Core Workflow: Analysis & Design

Define a Candidate Architecture

Core Workflow: Configuration & Change Management

Manage Change Requests

Complete Change Request Form

The Change Request Form is a formally submitted artifact that is used to track all requests (including new features, enhancement requests, defects, changed requirements, etc.) along with related status information throughout the project lifecycle. All change history will be maintained with the CR, including all state changes along with dates and reasons for the change. This information will be available for any repeat reviews and for final closing. An example Change Request Form is provided in Artifact: Change Requests.

Submit the Change Request

Once the CR is completed, it should be submitted through the proper channels to assure compliance with the established Change Request Management Process. Any stakeholder on the project can submit a Change Request (CR). The CR is logged into the CR Tracking System (e.g., ClearQuest) and is placed into the CCB Review Queue, by setting the CR state to Submitted.